Conversation
…k on actual devices
…k on actual devices
…ey/Frank into remove-uiautomation-in-ios7
|
I posted my thought on this to the Frank mailing list: https://groups.google.com/forum/#!topic/frank-discuss/9Da9wT66kJI |
|
Hey all, I have run into a bit of a road-bump with PublicAutomation and Any less than 0.55, and the row will slide back closed. Any further, and However, I never see the delete button. Even during the start of the slide, So my question is this: Is anyone familiar with UIAutomation (the Thanks! On Wed, Jan 22, 2014 at 11:54 AM, Pete Hodgson notifications@github.comwrote:
|
|
Might be worth posting this question on the Frank mailing list. Cheers, PeteTyped on a little bitty keyboard
|
|
Quite right. I thought this would go to the mailing list. Sorry! On Tue, Feb 4, 2014 at 11:13 AM, Pete Hodgson notifications@github.comwrote:
|
Conflicts: Frank.xcodeproj/project.pbxproj lib/PublicAutomation
… empty string instead of nil
Update remove-uiautomation branch
This is, unfortunately, not a clear win, so I'm sending it out for feedback.
I came to the conclusion that there was no way to use the UIAutomation APIs which Pete figured out how to wrap ( http://blog.thepete.net/blog/2012/08/20/introducing-publicautomation/ ). The core issue here is that Apple has locked it off, and you need a special entitlement to use it. You cannot generate this entitlement yourself when signing your app. Only Apple-approved apps can use UIAutomation.
So I switched Frank to simulate UIEvents, which is what KIF does. In fact, most of this change pulls in some more code from KIF. I don't think there's a licensing problem here, since we're already using some KIF code, but please feel free to correct me. I used KIF because I wanted to get this done as quickly as possible. As a result, the code is not as clean as it could be, but we can fix that in the future.
As part of this change, I updated the Controls example for iOS 7. I was able to run all of its tests on my iPhone 5 running iOS 7, as well as in the simulator.